Skip to main content
Check and provide your planning data

BETA This is a new service – your feedback will help us to improve it.

Back to dataset table
East Hampshire District Council

Tree

There is a problem

  • 1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1118

reference
510-tree-1
name
1118
tree-preservation-order

undefined

510-tpo-1
uprn
address-text
point
POINT (-1.021894 50.898447)
geometry
MULTIPOLYGON (((-1.021823 50.898439,-1.021826 50.898453,-1.021836 50.898466,-1.021851 50.898476,-1.021871 50.898482,-1.021893 50.898485,-1.021915 50.898483,-1.021935 50.898476,-1.021951 50.898467,-1.021961 50.898454,-1.021965 50.898440,-1.021962 50.898426,-1.021952 50.898414,-1.021937 50.898404,-1.021917 50.898397,-1.021895 50.898395,-1.021873 50.898397,-1.021853 50.898403,-1.021837 50.898413,-1.021827 50.898425,-1.021823 50.898439)))
notes
felled-date
entry-date
2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL